Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The system must require an administrator to unlock an account locked due to excessive login failures.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-64029 | VCWN-06-000047 | SV-78519r1_rule | Medium |
| Description |
|---|
| By limiting the number of failed login attempts, the risk of unauthorized access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account. |
| STIG | Date |
|---|---|
| VMware vSphere vCenter Server Version 6 Security Technical Implementation Guide | 2017-07-11 |
Details
| Check Text ( C-64781r1_chk ) |
|---|
| From the vSphere Web Client go to Administration >> Single Sign-On >> Configuration >> Policies >> Lockout Policy. View the values for the lockout policies. The following lockout policy should be set at follows: Unlock time: 0 If this account lockout policy is not configured as stated, this is a finding. |
| Fix Text (F-69959r1_fix) |
|---|
| From the vSphere Web Client go to Administration >> Single Sign-On >> Configuration >> Policies >> Lockout Policy. Click Edit. Set the Unlock time to 0 and click OK. |